Systems and methods for protecting header fields in a message

ABSTRACT

Embodiments of the systems and methods described herein facilitate the transmitting, receiving, and processing of encoded messages wherein the header fields in the message header are protected. In one embodiment, the contents of the header fields to be protected are inserted into the message body as one or more additional lines of text, for example, prior to encoding and transmitting the message to a message recipient. Upon receipt of the message, the message recipient processes the encoded message such that the contents of the protected header fields can be extracted from the message body. Accordingly, by inserting the contents of the header fields to be protected into the message body, the header fields may be protected using existing standards and protocols for facilitating secure message communication.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.12/394,766, filed Feb. 27, 2009. The entire contents of U.S. patentapplication Ser. No. 12/394,766 are hereby incorporated by reference.

RELEVANT FIELD

Embodiments described herein relate generally to the processing ofmessages (e.g. electronic mail messages), and more specifically to theprocessing of encoded messages.

BACKGROUND

An electronic mail (“e-mail”) message may comprise one or more of thefollowing: a message header, a message body, optionally one or moreencoded attachments, one or more encrypted session keys (e.g. if themessage is encrypted), and digital signature and signature-relatedinformation. The message header may comprise the following headerfields, for example: “To”, “From”, “Cc”, “Bcc”, “Date”, “Reply-To”, and“Subject”.

Electronic mail messages may be generally encoded using one of a numberof known protocols to facilitate secure message communication. Examplesof known standards and protocols for facilitating secure messagecommunication include the Secure Multiple Internet Mail Extensions(“S/MIME”) protocol and the Pretty Good Privacy™ (PGP) protocol.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of embodiments of the systems and methodsdescribed herein, and to show more clearly how they may be carried intoeffect, reference will be made, by way of example, to the accompanyingdrawings in which:

FIG. 1 is a block diagram of a mobile device in one exampleimplementation;

FIG. 2 is a block diagram of a communication subsystem component of themobile device of FIG. 1;

FIG. 3 is a block diagram of a node of a wireless network;

FIG. 4 is a block diagram illustrating components of a host system inone example configuration;

FIG. 5 is a block diagram illustrating components of an example of anencoded message;

FIGS. 6A and 6B are flowcharts illustrating acts of a method oftransmitting an encoded message from a computing device (i.e. themessage sender's device) to a message recipient at another computingdevice in accordance with at least one embodiment;

FIGS. 7A, 7B, 7C and 7D are flowcharts illustrating acts of a method ofreceiving an encoded message at a computing device (i.e. the messagerecipient's device) from a message sender at another computing device inaccordance with at least one embodiment;

FIGS. 8A, 8B, 8C, 8D and 8E are examples of messages from theperspective of the message sender's device, the message comprising asubject field to be protected, in accordance with at least oneembodiment; and

FIGS. 9A and 9B are examples of messages from the perspective of themessage recipient's device, the message comprising the contents of aprotected subject field inserted into the message body, in accordancewith at least one embodiment.

DETAILED DESCRIPTION

Some embodiments of the systems and methods described herein makereference to a mobile device. A mobile device may be a two-waycommunication device with advanced data communication capabilitieshaving the capability to communicate with other computer systems. Amobile device may also include the capability for voice communications.Depending on the functionality provided by a mobile device, it may bereferred to as a data messaging device, a two-way pager, a cellulartelephone with data messaging capabilities, a wireless Internetappliance, or a data communication device (with or without telephonycapabilities), for example. A mobile device may communicate with otherdevices through a network of transceiver stations.

To aid the reader in understanding the structure of a mobile device andhow it communicates with other devices, reference is made to FIGS. 1through 3.

Referring first to FIG. 1, a block diagram of a mobile device in oneexample implementation is shown generally as 100. Mobile device 100comprises a number of components, the controlling component beingmicroprocessor 102. Microprocessor 102 controls the overall operation ofmobile device 100. Communication functions, including data and voicecommunications, may be performed through communication subsystem 104.Communication subsystem 104 may be configured to receive messages fromand send messages to a wireless network 200. In one exampleimplementation of mobile device 100, communication subsystem 104 may beconfigured in accordance with the Global System for Mobile Communication(GSM) and General Packet Radio Services (GPRS) standards. The GSM/GPRSwireless network is used worldwide and it is expected that thesestandards may be supplemented or superseded eventually by Enhanced DataGSM Environment (EDGE) and Universal Mobile Telecommunications Service(UMTS), and Ultra Mobile Broadband (UMB), etc. New standards are stillbeing defined, but it is believed that they will have similarities tothe network behaviour described herein, and it will also be understoodby persons skilled in the art that the embodiments of the presentdisclosure are intended to use any other suitable standards that aredeveloped in the future. The wireless link connecting communicationsubsystem 104 with network 200 represents one or more different RadioFrequency (RF) channels, operating according to defined protocolsspecified for GSM/GPRS communications. With newer network protocols,these channels are capable of supporting both circuit switched voicecommunications and packet switched data communications.

Although the wireless network associated with mobile device 100 is aGSM/GPRS wireless network in one example implementation of mobile device100, other wireless networks may also be associated with mobile device100 in variant implementations. Different types of wireless networksthat may be employed include, for example, data-centric wirelessnetworks, voice-centric wireless networks, and dual-mode networks thatcan support both voice and data communications over the same physicalbase stations. Combined dual-mode networks include, but are not limitedto, Code Division Multiple Access (CDMA) or CDMA2000 networks, GSM/GPRSnetworks (as mentioned above), and future third-generation (3G) networkslike EDGE and UMTS. Some older examples of data-centric networks includethe Mobitex™ Radio Network and the DataTAC™ Radio Network. Examples ofolder voice-centric data networks include Personal Communication Systems(PCS) networks like GSM and Time Division Multiple Access (TDMA)systems. Other network communication technologies that may be employedinclude, for example, Integrated Digital Enhanced Network (iDEN™)Evolution-Data Optimized (EV-DO), and High Speed Packet Access (HSPA),etc.

Microprocessor 102 may also interact with additional subsystems such asa Random Access Memory (RAM) 106, flash memory 108, display 110,auxiliary input/output (I/O) subsystem 112, serial port 114, keyboard116, speaker 118, microphone 120, short-range communications subsystem122 and other device subsystems 124.

Some of the subsystems of mobile device 100 performcommunication-related functions, whereas other subsystems may provide“resident” or on-device functions. By way of example, display 110 andkeyboard 116 may be used for both communication-related functions, suchas entering a text message for transmission over network 200, as well asdevice-resident functions such as a calculator or task list. Operatingsystem software used by microprocessor 102 is typically stored in apersistent store such as flash memory 108, which may alternatively be aread-only memory (ROM) or similar storage element (not shown). Thoseskilled in the art will appreciate that the operating system, specificdevice applications, or parts thereof, may be temporarily loaded into avolatile store such as RAM 106.

Mobile device 100 may send and receive communication signals overnetwork 200 after network registration or activation procedures havebeen completed. Network access may be associated with a subscriber oruser of a mobile device 100. To identify a subscriber, mobile device 100may provide for a Subscriber Identity Module (“SIM”) card 126 to beinserted in a SIM interface 128 in order to communicate with a network.SIM 126 may be one example type of a conventional “smart card” used toidentify a subscriber of mobile device 100 and to personalize the mobiledevice 100, among other things. Without SIM 126, mobile device 100 maynot be fully operational for communication with network 200. Byinserting SIM 126 into SIM interface 128, a subscriber may access allsubscribed services. Services may include, without limitation: webbrowsing and messaging such as e-mail, voice mail, Short Message Service(SMS), and Multimedia Messaging Services (MMS). More advanced servicesmay include, without limitation: point of sale, field service and salesforce automation. SIM 126 may include a processor and memory for storinginformation. Once SIM 126 is inserted in SIM interface 128, it may becoupled to microprocessor 102. In order to identify the subscriber, SIM126 may contain some user parameters such as an International MobileSubscriber Identity (IMSI). By using SIM 126, a subscriber may notnecessarily be bound by any single physical mobile device. SIM 126 maystore additional subscriber information for a mobile device as well,including datebook (or calendar) information and recent callinformation.

Mobile device 100 may be a battery-powered device and may comprise abattery interface 132 for receiving one or more rechargeable batteries130. Battery interface 132 may be coupled to a regulator (not shown),which assists battery 130 in providing power V+ to mobile device 100.Although current technology makes use of a battery, future technologiessuch as micro fuel cells may provide power to mobile device 100. In someembodiments, mobile device 100 may be solar-powered.

Microprocessor 102, in addition to its operating system functions,enables execution of software applications on mobile device 100. A setof applications that control basic device operations, including data andvoice communication applications, may be installed on mobile device 100during its manufacture. Another application that may be loaded ontomobile device 100 is a personal information manager (PIM). A PIM hasfunctionality to organize and manage data items of interest to asubscriber, such as, but not limited to, e-mail, calendar events, voicemails, appointments, and task items. A PIM application has the abilityto send and receive data items via wireless network 200. PIM data itemsmay be seamlessly integrated, synchronized, and updated via wirelessnetwork 200 with the mobile device subscriber's corresponding data itemsstored and/or associated with a host computer system. This functionalitymay create a mirrored host computer on mobile device 100 with respect tosuch items. This can be particularly advantageous where the hostcomputer system is the mobile device subscriber's office computersystem.

Additional applications may also be loaded onto mobile device 100through network 200, auxiliary I/O subsystem 112, serial port 114,short-range communications subsystem 122, or any other suitablesubsystem 124. This flexibility in application installation increasesthe functionality of mobile device 100 and may provide enhancedon-device functions, communication-related functions, or both. Forexample, secure communication applications may enable electroniccommerce functions and other such financial transactions to be performedusing mobile device 100.

Serial port 114 enables a subscriber to set preferences through anexternal device or software application and extends the capabilities ofmobile device 100 by providing for information or software downloads tomobile device 100 other than through a wireless communication network.The alternate download path may, for example, be used to load anencryption key onto mobile device 100 through a direct and thus reliableand trusted connection to provide secure device communication.

Short-range communications subsystem 122 provides for communicationbetween mobile device 100 and different systems or devices, without theuse of network 200. For example, subsystem 122 may include an infrareddevice and associated circuits and components for short-rangecommunication. Examples of short range communication include standardsdeveloped by the Infrared Data Association (IrDA), Bluetooth®, and the802.11 family of standards (Wi-Fi®) developed by IEEE.

In use, a received signal such as a text message, an e-mail message, orweb page download is processed by communication subsystem 104 and inputto microprocessor 102. Microprocessor 102 then processes the receivedsignal for output to display 110 or alternatively to auxiliary I/Osubsystem 112. A subscriber may also compose data items, such as e-mailmessages, for example, using keyboard 116 in conjunction with display110 and possibly auxiliary I/O subsystem 112. Auxiliary subsystem 112may include devices such as: a touch screen, mouse, track ball, infraredfingerprint detector, or a roller wheel with dynamic button pressingcapability. Keyboard 116 may comprise an alphanumeric keyboard and/ortelephone-type keypad, for example. A composed item may be transmittedover network 200 through communication subsystem 104.

For voice communications, the overall operation of mobile device 100 maybe substantially similar, except that the received signals may beprocessed and output to speaker 118, and signals for transmission may begenerated by microphone 120. Alternative voice or audio I/O subsystems,such as a voice message recording subsystem, may also be implemented onmobile device 100. Although voice or audio signal output is accomplishedprimarily through speaker 118, display 110 may also be used to provideadditional information such as the identity of a calling party, durationof a voice call, or other voice call related information.

Referring now to FIG. 2, a block diagram of the communication subsystemcomponent 104 of FIG. 1 is shown. Communication subsystem 104 maycomprise a receiver 150, a transmitter 152, one or more embedded orinternal antenna elements 154, 156, Local Oscillators (LOs) 158, and aprocessing module such as a Digital Signal Processor (DSP) 160.

The particular design of communication subsystem 104 is dependent uponthe network 200 in which mobile device 100 is intended to operate; thus,it should be understood that the design illustrated in FIG. 2 servesonly as one example. Signals received by antenna 154 through network 200are input to receiver 150, which may perform such common receiverfunctions as signal amplification, frequency down conversion, filtering,channel selection, and analog-to-digital (A/D) conversion. A/Dconversion of a received signal allows more complex communicationfunctions such as demodulation and decoding to be performed in DSP 160.In a similar manner, signals to be transmitted are processed, includingmodulation and encoding, by DSP 160. These DSP-processed signals areinput to transmitter 152 for digital-to-analog (D/A) conversion,frequency up conversion, filtering, amplification and transmission overnetwork 200 via antenna 156. DSP 160 not only processes communicationsignals, but also provides for receiver and transmitter control. Forexample, the gains applied to communication signals in receiver 150 andtransmitter 152 may be adaptively controlled through automatic gaincontrol algorithms implemented in DSP 160.

The wireless link between mobile device 100 and a network 200 maycontain one or more different channels, typically different RF channels,and associated protocols used between mobile device 100 and network 200.A RF channel is generally a limited resource, typically due to limits inoverall bandwidth and limited battery power of mobile device 100.

When mobile device 100 is fully operational, transmitter 152 may betypically keyed or turned on only when it is sending to network 200 andmay otherwise be turned off to conserve resources. Similarly, receiver150 may be periodically turned off to conserve power until it is neededto receive signals or information (if at all) during designated timeperiods.

Referring now to FIG. 3, a block diagram of a node of a wireless networkis shown as 202. In practice, network 200 comprises one or more nodes202. Mobile device 100 communicates with a node 202 within wirelessnetwork 200. In the example implementation of FIG. 3, node 202 isconfigured in accordance with GPRS and GSM technologies; however, inother embodiments, different standards may be implemented as discussedin more detail above. Node 202 includes a base station controller (BSC)204 with an associated tower station 206, a Packet Control Unit (PCU)208 added for GPRS support in GSM, a Mobile Switching Center (MSC) 210,a Home Location Register (HLR) 212, a Visitor Location Registry (VLR)214, a Serving GPRS Support Node (SGSN) 216, a Gateway GPRS Support Node(GGSN) 218, and a Dynamic Host Configuration Protocol (DHCP) server 220.This list of components is not meant to be an exhaustive list of thecomponents of every node 202 within a GSM/GPRS network, but rather alist of components that are commonly used in communications throughnetwork 200.

In a GSM network, MSC 210 is coupled to BSC 204 and to a landlinenetwork, such as a Public Switched Telephone Network (PSTN) 222 tosatisfy circuit switched requirements. The connection through PCU 208,SGSN 216 and GGSN 218 to the public or private network (Internet) 224(also referred to herein generally as a shared network infrastructure)represents the data path for GPRS capable mobile devices. In a GSMnetwork extended with GPRS capabilities, BSC 204 also contains a PacketControl Unit (PCU) 208 that connects to SGSN 216 to controlsegmentation, radio channel allocation and to satisfy packet switchedrequirements. To track mobile device location and availability for bothcircuit switched and packet switched management, HLR 212 is sharedbetween MSC 210 and SGSN 216. Access to VLR 214 is controlled by MSC210.

Station 206 may be a fixed transceiver station. Station 206 and BSC 204together may form the fixed transceiver equipment. The fixed transceiverequipment provides wireless network coverage for a particular coveragearea commonly referred to as a “cell”. The fixed transceiver equipmenttransmits communication signals to and receives communication signalsfrom mobile devices within its cell via station 206. The fixedtransceiver equipment normally performs such functions as modulation andpossibly encoding and/or encryption of signals to be transmitted to themobile device in accordance with particular, usually predetermined,communication protocols and parameters, under control of its controller.The fixed transceiver equipment similarly demodulates and possiblydecodes and decrypts, if necessary, any communication signals receivedfrom mobile device 100 within its cell. Communication protocols andparameters may vary between different nodes. For example, one node mayemploy a different modulation scheme and operate at differentfrequencies than other nodes.

For all mobile devices 100 registered with a specific network, permanentconfiguration data such as a user profile may be stored in HLR 212. HLR212 may also contain location information for each registered mobiledevice and can be queried to determine the current location of a mobiledevice. MSC 210 is responsible for a group of location areas and storesthe data of the mobile devices currently in its area of responsibilityin VLR 214. Further VLR 214 also contains information on mobile devicesthat are visiting other networks. The information in VLR 214 includespart of the permanent mobile device data transmitted from HLR 212 to VLR214 for faster access. By moving additional information from a remoteHLR 212 node to VLR 214, the amount of traffic between these nodes canbe reduced so that voice and data services can be provided with fasterresponse times while requiring less use of computing resources.

SGSN 216 and GGSN 218 are elements that may be added for GPRS support;namely packet switched data support, within GSM. SGSN 216 and MSC 210have similar responsibilities within wireless network 200 by keepingtrack of the location of each mobile device 100. SGSN 216 also performssecurity functions and access control for data traffic on network 200.GGSN 218 provides internetworking connections with external packetswitched networks and connects to one or more SGSNs 216 via an InternetProtocol (IP) backbone network operated within the network 200. Duringnormal operations, a given mobile device 100 performs a “GPRS Attach” toacquire an IP address and to access data services. This normally is notpresent in circuit switched voice channels as Integrated ServicesDigital Network (ISDN) addresses may be generally used for routingincoming and outgoing calls. Currently, GPRS capable networks may useprivate, dynamically assigned IP addresses, thus requiring a DHCP server220 connected to the GGSN 218. There are many mechanisms for dynamic IPassignment, including using a combination of a Remote AuthenticationDial-In User Service (RADIUS) server and DHCP server, for example. Oncethe GPRS Attach is complete, a logical connection is established from amobile device 100, through PCU 208, and SGSN 216 to an Access Point Node(APN) within GGSN 218, for example. The APN represents a logical end ofan IP tunnel that can either access direct Internet compatible servicesor private network connections. The APN also represents a securitymechanism for network 200, insofar as each mobile device 100 must beassigned to one or more APNs and mobile devices 100 cannot generallyexchange data without first performing a GPRS Attach to an APN that ithas been authorized to use. The APN may be considered to be similar toan Internet domain name such as “myconnection.wireless.com”.

Once the GPRS Attach is complete, a tunnel is created and all traffic isexchanged within standard IP packets using any protocol that can besupported in IP packets. This includes tunneling methods such as IP overIP as in the case with some IPSecurity (IPsec) connections used withVirtual Private Networks (VPN). These tunnels are also referred to asPacket Data Protocol (PDP) Contexts and there are a limited number ofthese available in the network 200. To maximize use of the PDP Contexts,network 200 will run an idle timer for each PDP Context to determine ifthere is a lack of activity. When a mobile device 100 is not using itsPDP Context, the PDP Context can be deallocated and the IP addressreturned to the IP address pool managed by DHCP server 220.

Referring now to FIG. 4, a block diagram illustrating components of ahost system in one example configuration is shown. Host system 250 willtypically be a corporate office or other local area network (LAN), butmay instead be a home office computer or some other private system, forexample, in variant implementations. In this example shown in FIG. 4,host system 250 is depicted as a LAN of an organization to which a userof mobile device 100 belongs.

LAN 250 comprises a number of network components connected to each otherby LAN connections 260. For instance, a user's desktop computing device(“desktop computer”) 262 a with an accompanying cradle 264 for theuser's mobile device 100 may be situated on LAN 250. Cradle 264 formobile device 100 may be coupled to computer 262 a by a serial or aUniversal Serial Bus (USB) connection, for example. Other user computers262 b are also situated on LAN 250, and each may or may not be equippedwith an accompanying cradle 264 for a mobile device. Cradle 264facilitates the loading of information (e.g. PIM data, private symmetricencryption keys to facilitate secure communications between mobiledevice 100 and LAN 250) from user computer 262 a to mobile device 100,and may be particularly useful for bulk information updates oftenperformed in initializing mobile device 100 for use. The informationdownloaded to mobile device 100 may include S/MIME certificates or PGPkeys used in the exchange of messages.

It will be understood by persons skilled in the art that user computers262 a, 262 b will typically be also connected to other peripheraldevices not explicitly shown in FIG. 4. Furthermore, only a subset ofnetwork components of LAN 250 are shown in FIG. 4 for ease ofexposition, and it will be understood by persons skilled in the art thatLAN 250 will comprise additional components not explicitly shown in FIG.4, for this example configuration. More generally, LAN 250 may representa smaller part of a larger network [not shown] of the organization, andmay comprise different components and/or be arranged in differenttopologies than that shown in the example of FIG. 4.

In this example, mobile device 100 communicates with LAN 250 through anode 202 of wireless network 200 and a shared network infrastructure 224such as a service provider network or the public Internet. Access to LAN250 may be provided through one or more routers [not shown], andcomputing devices of LAN 250 may operate from behind a firewall or proxyserver 266.

In a variant implementation, LAN 250 comprises a wireless VPN router[not shown] to facilitate data exchange between the LAN 250 and mobiledevice 100. The concept of a wireless VPN router is new in the wirelessindustry and implies that a VPN connection can be established directlythrough a specific wireless network to mobile device 100. Thepossibility of using a wireless VPN router has only recently beenavailable and could be used when the new Internet Protocol (IP) Version6 (IPV6) arrives into IP-based wireless networks. This new protocol willprovide enough IP addresses to dedicate an IP address to every mobiledevice, making it possible to push information to a mobile device at anytime. An advantage of using a wireless VPN router is that it could be anoff-the-shelf VPN component, not requiring a separate wireless gatewayand separate wireless infrastructure to be used. A VPN connection mayinclude, for example, a Transmission Control Protocol (TCP)/IP or UserDatagram Protocol (UDP)/IP connection to deliver the messages directlyto mobile device 100 in this variant implementation.

Messages intended for a user of mobile device 100 are initially receivedby a message server 268 of LAN 250. Such messages may originate from anyof a number of sources. For instance, a message may have been sent by asender from a computer 262 b within LAN 250, from a different mobiledevice [not shown] connected to wireless network 200 or to a differentwireless network, or from a different computing device or other devicecapable of sending messages, via the shared network infrastructure 224,and possibly through an application service provider (ASP) or Internetservice provider (ISP), for example.

Message server 268 typically acts as the primary interface for theexchange of messages, particularly e-mail messages, within theorganization and over the shared network infrastructure 224. Each userin the organization that has been set up to send and receive messages istypically associated with a user account managed by message server 268.One example of a message server 268 is a Microsoft Exchange™ Server. Insome implementations. LAN 250 may comprise multiple message servers 268.Message server 268 may also be adapted to provide additional functionsbeyond message management, including the management of data associatedwith calendars and task lists, for example.

When messages are received by message server 268, they are typicallystored in a message store [not explicitly shown], from which messagescan be subsequently retrieved and delivered to users. For instance, ane-mail client application operating on a user's computer 262 a mayrequest the e-mail messages associated with that user's account storedon message server 268. These messages may then typically be retrievedfrom message server 268 and stored locally on computer 262 a.

When operating mobile device 100, the user may wish to have e-mailmessages retrieved for delivery to the mobile device 100. An e-mailclient application operating on mobile device 100 may request messagesassociated with the user's account from message server 268. The e-mailclient may be configured (either by the user or by an administrator,possibly in accordance with an organization's information technology(IT) policy) to make this request at the direction of the user, at somepre-defined time interval, or upon the occurrence of some pre-definedevent. In some implementations, mobile device 100 is assigned its owne-mail address, and messages addressed specifically to mobile device 100may be automatically redirected to mobile device 100 as they arereceived by message server 268.

To facilitate the wireless communication of messages and message-relateddata between mobile device 100 and components of LAN 250, a number ofwireless communications support components 270 may be provided. In thisexample implementation, wireless communications support components 270may comprise a message management server 272, for example. Messagemanagement server 272 may be used to specifically provide support forthe management of messages, such as e-mail messages, that are to behandled by mobile devices. Generally, while messages are still stored onmessage server 268, message management server 272 may be used to controlwhen, if, and how messages should be sent to mobile device 100. Messagemanagement server 272 also facilitates the handling of messages composedon mobile device 100, which are sent to message server 268 forsubsequent delivery.

For example, message management server 272 may: monitor the user's“mailbox” (e.g. the message store associated with the user's account onmessage server 268) for new e-mail messages; apply user-definablefilters to new messages to determine if and how the messages will berelayed to the user's mobile device 100; compress and encrypt newmessages (e.g. using an encryption technique such as Data EncryptionStandard (DES) or Triple DES) and push them to mobile device 100 via theshared network infrastructure 224 and wireless network 200; and receivemessages composed on mobile device 100 (e.g. encrypted using TripleDES), decrypt and decompress the composed messages, re-format thecomposed messages if desired so that they will appear to have originatedfrom the user's computer 262 a, and re-route the composed messages tomessage server 268 for delivery.

Certain properties or restrictions associated with messages that are tobe sent from and/or received by mobile device 100 can be defined (e.g.by an administrator in accordance with IT policy) and enforced bymessage management server 272. These may include whether mobile device100 may receive encrypted and/or signed messages, minimum encryption keysizes, whether outgoing messages must be encrypted and/or signed, andwhether copies of all secure messages sent from mobile device 100 are tobe sent to a pre-defined copy address, for example.

Message management server 272 may also be adapted to provide othercontrol functions, such as only pushing certain message information orpre-defined portions (e.g. “blocks”) of a message stored on messageserver 268 to mobile device 100. For example, when a message isinitially retrieved by mobile device 100 from message server 268,message management server 272 is adapted to push only the first part ofa message to mobile device 100, with the part being of a pre-definedsize (e.g. 2 KB). The user can then request more of the message, to bedelivered in similar-sized blocks by message management server 272 tomobile device 100, possibly up to a maximum pre-defined message size.

Accordingly, message management server 272 facilitates better controlover the type of data and the amount of data that is communicated tomobile device 100, and can help to minimize potential waste of bandwidthor other resources.

It will be understood by persons skilled in the art that messagemanagement server 272 need not be implemented on a separate physicalserver in LAN 250 or other network. For example, some or all of thefunctions associated with message management server 272 may beintegrated with message server 268, or some other server in LAN 250.Furthermore, LAN 250 may comprise multiple message management servers272, particularly in variant implementations where a large number ofmobile devices are supported.

While Simple Mail Transfer Protocol (SMTP), RFC822 headers, andMultipurpose Internet Mail Extensions (MIME) body parts may be used todefine the format of a typical e-mail message not requiring encoding,Secure/MIME (S/MIME), a version of the MIME protocol, may be used in thecommunication of encoded messages (i.e. in secure messagingapplications). S/MIME enables end-to-end authentication andconfidentiality, and provides data integrity and privacy from the timean originator of a message sends a message until it is decoded and readby the message recipient. Other standards and protocols may be employedto facilitate secure message communication, such as Pretty Good Privacy™(PGP) and variants of PGP such as OpenPGP, for example. It will beunderstood that where reference is generally made to “PGP” herein, theterm is intended to encompass any of a number of variant implementationsbased on the more general PGP scheme.

Secure messaging protocols such as S/MIME and PGP-based protocols relyon public and private encryption keys to provide confidentiality andintegrity. Data encoded using a private key of a private key/public keypair can only be decoded using the corresponding public key of the pair,and data encoded using a public key of a private key/public key pair canonly be decoded using the corresponding private key of the pair. It isintended that private key information never be made public, whereaspublic key information is shared.

For example, if a sender wishes to send message data to a recipient inencrypted form, the recipient's public key is used to encrypt themessage data, which can then be decrypted only using the recipient'sprivate key. Alternatively, in some encoding techniques, a one-timesession key is generated and used to encrypt the message data, typicallywith a symmetric encryption technique (e.g. Triple DES). The session keyis then encrypted using the recipient's public key (e.g. with a publickey encryption algorithm such as RSA), which can then be decrypted onlyusing the recipient's private key. The decrypted session key can then beused to decrypt the encrypted message data. The message header maycomprise data specifying the particular encryption scheme that must beused to decrypt the encrypted message data. Other encryption techniquesbased on public key cryptography may be used in variant implementations.However, in each of these cases, only the recipient's private key may beused to facilitate successful decryption of the encrypted message data,and in this way, the confidentiality of that data can be maintained.

As a further example, a sender may sign message data using a digitalsignature. A digital signature generally comprises a digest of themessage data being signed (e.g. a hash of the message data being signed)encoded using the sender's private key, which can then be appended tothe outgoing message. To verify the digital signature when received, therecipient uses the same technique as the sender (e.g. using the samestandard hash algorithm) to obtain a digest of the received messagedata. The recipient also uses the sender's public key to decode thedigital signature, in order to obtain what should be a matching digestfor the received message data. If the digests of the received message donot match, this suggests that either the message data was changed duringtransport and/or the message data did not originate from the senderwhose public key was used for verification. Digital signature algorithmsare designed in such a way that only someone with knowledge of thesender's private key should be able to encode a digital signature thatthe recipient will decode correctly using the sender's public key.Therefore, by verifying a digital signature in this way, authenticationof the sender and message integrity can be maintained.

In the description of exemplary embodiments herein, the term “secureencoding” is used. When reference is made to the application of a secureencoding to message data, this means that the message data is encodedusing an encoding technique. As noted above, an act of encoding messagedata may include either encrypting the message data or signing themessage data. It will be understood that encoded message data may alsobe both encrypted and signed. As used in this disclosure, “signed and/orencrypted” means signed or encrypted or both.

in S/MIME, the authenticity of public keys used in these operations maybe validated using certificates. A certificate is a digital documentissued, for example, by a certificate authority (CA). Certificates areused to authenticate the association between users and their publickeys, and essentially, provides a level of trust in the authenticity ofthe users' public keys. Certificates contain information about thecertificate holder, with certificate contents typically formatted inaccordance with an accepted standard (e.g. X.509). The certificates aretypically digitally signed by the certificate authority.

In PGP-based systems, a PGP key is used, which is like an S/MIMEcertificate in that it contains public information including a publickey and information on the key holder or owner. Unlike S/MIMEcertificates, however, PGP keys are not generally issued by acertificate authority, and the level of trust in the authenticity of aPGP key typically requires verifying that a trusted individual hasvouched for the authenticity of a given PGP key.

While the term “PGP key” may not be commonly used interchangeably withthe term “certificate”, in the context of the embodiments describedherein and for the purposes of the specification and in the claims, a“certificate” is deemed to include similar constructs of other securemessaging protocols such as a PGP key.

Standard e-mail security protocols typically facilitate secure messagetransmission between non-mobile computing devices (e.g. computers 262 a,262 b of FIG. 4; remote desktop devices). In order that signed messagesreceived from senders may be read from mobile device 100 and thatencrypted messages be sent from mobile device 100, mobile device 100 maybe adapted to store public keys (e.g. in S/MIME certificates, PGP keys)of other individuals. Keys stored on a user's computer 262 a may bedownloaded from computer 262 a to mobile device 100 through cradle 264,for example.

Mobile device 100 may also be adapted to store the private key of thepublic key/private key pair associated with the user, so that the userof mobile device 100 can sign outgoing messages composed on mobiledevice 100, and decrypt messages sent to the user encrypted with theuser's public key. The private key may be downloaded to mobile device100 from the user's computer 262 a through cradle 264, for example. Theprivate key may be exchanged between the computer 262 a and mobiledevice 100 so that the user may share one identity and one method foraccessing messages.

User computers 262 a, 262 b can obtain S/MIME certificates and PGP keysfrom a number of sources, for storage on computers 262 a, 262 b and/ormobile devices (e.g. mobile device 100) in a key store, for example. Thesources of these certificates and keys may be private (e.g. dedicatedfor use within an organization) or public, may reside locally orremotely, and may be accessible from within an organization's privatenetwork or through the Internet, for example. In the example shown inFIG. 4, multiple public key infrastructure (PKI) servers 280 associatedwith the organization reside on LAN 250. PKI servers 280 include a CAserver 282 that may be used for issuing S/MIME certificates, aLightweight Directory Access Protocol (LDAP) server 284 that may be usedto search for and download S/MIME certificates and/or PGP keys (e.g. forindividuals within the organization), and an Online Certificate StatusProtocol (OCSP) server 286 that may be used to verify the revocationstatus of S/MIME certificates, for example.

Certificates and/or PGP keys may be retrieved from LDAP server 284 by auser computer 262 a, for example, to be downloaded to mobile device 100via cradle 264. However, in a variant implementation, LDAP server 284may be accessed directly (i.e. “over the air” in this context) by mobiledevice 100, and mobile device 100 may search for and retrieve individualcertificates and PGP keys through a mobile data server 288. Similarly,mobile data server 288 may be adapted to allow mobile device 100 todirectly query OCSP server 286 to verify the revocation status of S/MIMEcertificates.

In variant implementations, only selected PKI servers 280 may be madeaccessible to mobile devices (e.g. allowing certificates to bedownloaded only from a user's computer 262 a, 262 b, while allowing therevocation status of certificates to be checked from mobile device 100).

In variant implementations, certain PKI servers 280 may be madeaccessible only to mobile devices registered to particular users, asspecified by an IT administrator, possibly in accordance with an ITpolicy, for example.

Other sources of S/MIME certificates and PGP keys [not shown] mayinclude a Windows certificate or key store, another secure certificateor key store on or outside LAN 250, and smart cards, for example.

Referring now to FIG. 5, a block diagram illustrating components of oneexample of an encoded message, as may be received by a message server(e.g. message server 268 of FIG. 4) and forwarded to a user (e.g. ofmobile device 100), is shown generally as 350. Encoded message 350 maycomprise one or more of the following: a message header 352, one or moreencrypted session keys 358 (e.g. if the message is encrypted), a messagebody 354, optionally one or more attachments 356 that may be encoded,digital signature and signature-related information 360. For example,message header 352 for message 350 may comprise one or more headerfields such as “To”, “From”, “Cc”, “Bcc”, “Date”, “Reply-To”, and“Subject”, and may also comprise message length indicators, andencryption and signature scheme identifiers, for example. Actual messagecontent (“message data”) is normally included in the message body 354and possibly in one or more attachments 356, which may be encrypted bythe sender, using a session key for example. If a session key is to beused, it is typically encrypted for each intended recipient using therespective public key for each recipient, and included in the message at358. If the message is signed, a digital signature and signature-relatedinformation 360 are included.

The format for an encoded message as shown in FIG. 5 is provided by wayof example only, and persons skilled in the art will understand thatencoded messages may exist in other formats. For example, encryptedsession keys 358 may be provided after message header 352 but beforemessage body 354. Depending on the specific secure messaging standard orprotocol employed, components of an encoded message may appear in adifferent order than shown in FIG. 5, and an encoded message may includefewer, additional, or different components, which may depend on whethermessage data of the encoded message is encrypted, signed or both.

Under existing standards and protocols, the header fields of an encodedelectronic mail message (e.g. message 350) are generally not secured(e.g. the contents of the header fields 352 are not encoded).Accordingly, a recipient of a message from a sender could change thecontents of one or more header fields (e.g. the subject) in the messageheader and resend the message with the changed header to a secondrecipient without decoding the message body. After the message isresent, there is no way for the second recipient to confirm that theoriginal contents in the header fields of the message header have notbeen tampered with. The digital signature of the message would stillverify and/or the encrypted message body would still be decryptable, andit would appear as if the message came directly from the sender sincetypically only the message body, and not the message header, is encoded(e.g. signed and/or encrypted) under existing standards and protocols.As a further example, a third party may intercept a message in transit,and surreptitiously change the content of the subject field in themessage header before it arrives at the recipient's device. Therecipient would not know that the original content of the subject fieldin the message header has been changed.

In the above-described examples, the present inventors recognized thatit may be desirable to preserve the integrity of the entire message,including the contents of the header fields in a message header. Theremay also be situations where confidentiality of the contents of theheader fields (e.g. the subject) in a message header of a message may bedesirable.

Embodiments of the systems and methods described herein generallyfacilitate the transmitting, receiving, and processing of encodedmessages wherein one or more header fields in a message header of themessage are protected. In one broad aspect, the contents of the one ormore header fields to be protected are inserted into the message body bythe message sender's device prior to encoding and transmitting themessage to a message recipient, but typically after a user has finishedcomposing the message and directed the device to send the message (e.g.by pressing a “send” button in a user interface provided on the sender'sdevice). Subsequently, upon receipt of the message, the messagerecipient's device will process the encoded message such that thecontents of the protected header fields can be extracted (e.g. viewedand/or verified). Accordingly, by inserting the contents of one or moreheader fields to be protected into the message body prior totransmission of the message from the sender's device to the recipient'sdevice, the contents of these header fields can then be protected usingexisting standards and protocols for facilitating secure messagecommunication, as the contents of these header fields are now containedwithin the message body.

In another broad aspect, there is provided a method and system fortransmitting an encoded message from a computing device (i.e. themessage sender's device) to a message recipient at another computingdevice, the message comprising a message header and a message body, themessage header comprising a plurality of header fields, the methodcomprising: inserting content of one or more header fields to beprotected of the plurality of header fields into the message body;encoding the message body; and transmitting the message after saidencoding to the message recipient, such that when the message isprocessed by the message recipient, the content of the one or moreheader fields to be protected is extractable from the message body. Insome embodiments, the one or more header fields to be protectedcomprises a subject field.

In another broad aspect, there is provided a method and system forreceiving an encoded message at a computing device (i.e. the messagerecipient's device) from a message sender at another computing device,the message comprising a message header and a message body, the messageheader comprising one or more header fields, the method comprising:receiving the encoded message from the message sender, wherein theencoded message comprises an encoded message body, the encoded messagebody comprising content of one or more protected header fields insertedby the message sender's device therein; decoding the encoded messagebody; and extracting the content of the one or more protected headerfields from the message body after said decoding. In some embodiments,the one or more protected header fields comprises a subject field.

In at least one example embodiment, the extracting comprises: searchingthe message body, after said decoding, for the content of the one ormore protected header fields; and where said content is located by saidsearching, inserting the content of the one or more protected headerfields located by said searching in a corresponding one or more headerfields of the message header.

In example embodiments, the sender's device may be a mobile device 100or some other computing device. Similarly, the recipient's device may bea mobile device 100 or some other computing device

These and other aspects and features of various embodiments will bedescribed in greater detail below. It should be noted by persons skilledin the art that the embodiments described above are applicable to bothsigned and/or encrypted messages.

Referring first to FIG. 6A, a flowchart illustrating acts of a method600 a of transmitting an encoded message (e.g. message 350 of FIG. 5)from a computing device (i.e. the message sender's device) to a messagerecipient at another computing device, wherein one or more header fieldsare to be protected, is shown, in accordance with at least oneembodiment.

In at least one embodiment, at least some of the acts of the method 600a are performed by a processor executing an application residing on acomputing device, such as a mobile device (e.g. mobile device 100 ofFIG. 1). In variant embodiments, the application may reside on acomputing device other than a mobile device. In at least one embodiment,the application is an e-mail application, although the acts of themethod may be performed in the execution of one or more differentapplications in variant embodiments.

By way of illustration, references are made below to the parts of theexample message as shown in FIG. 5.

At 610 a, a determination is made as to whether one or more headerfields in the message header 352 are to be protected. The determinationmay be based on input from the sender of the message 350, generally theuser of the computing device, or based on a pre-set configurationsetting, for example.

For example, the determination at 610 a may be made based on user inputprovided via a user interface, in which the user may be presented withan option and be required to indicate whether one or more header fieldsare to be protected, and if so, which header fields are to be protected.This may be done on a message-by-message basis, after the user hasfinished composing the message 350 and directed the computing device tosend the message 350 (e.g. by pressing a “send” button or similar optionin the user interface), for example. Alternatively, this may be donewhile the user is still composing the message 350 (e.g. after the userhas finished entering content into the message header 352, but before orwhile the user is entering content into the message body 354), andbefore the user has directed the device to send the message 350 (e.g. bypressing a “send” button or similar option in the user interface).Another alternative is that the option may be presented to the userprior to the composition of message 350, for example, upon installationof the application, or upon a powering on of the computing device. Theuser may be provided with the option of protecting selected headerfields, on a message-by-message basis, for all messages, or for allmessages meeting certain criteria (e.g. when the message is to be sentto one or more designated recipients). To be clear, all header fieldsmay be protected or a selected subset of header fields may be protectedas identified by a user.

In some other instances, there may be no option provided to the user atall. For example, the sender's device may be configured to automaticallyprotect all header fields or certain header fields. The protection ofheader fields may be initiated by an administrator, for example, via anIT policy or other configuration settings in variant embodiments.

Notwithstanding that a user may have manually selected which headerfields they would like to be protected at 610 a, it should be understoodby persons skilled in the art that this selection can be overridden bythe configuration settings as defined by the device or an administrator(e.g. via an IT policy), for example, in variant embodiments.

If it is not desired to protect any of the header fields, then the flowof method acts proceeds to 660 a where the message 350 (specifically, atleast the message body 354 and possibly message attachments 356) issecurely encoded using one of a number of known standards and protocolsfor facilitating secure message communication, for subsequenttransmission at 670 a to the intended message recipient.

However, if it is desired to protect one or more header fields, then theflow of method acts proceeds to 630 a. At 630 a, the contents of the oneor more header fields to be protected as determined at 610 a areinserted into the message body 354, for example, as one or moreadditional lines of text. In one example embodiment, the contents of theone or more header fields to be protected may be inserted into themessage body 354 as one or more additional lines of text prefaced by adescription, for example: “Secure <name of header field>: <contents ofheader field>” (e.g. “Secure subject: Do you want to go for lunch?”).The insertion of the header field contents into the message body 354 maybe done after the user has finished composing the message and directedthe device to send the message (e.g. by pressing a “send” button orsimilar option in a user interface). This insertion may be doneautomatically by the application, with no user intervention (i.e. notrequiring the user to manually insert the contents of the one or moreheader fields to be protected into the message body 354), which mayincrease user convenience.

By inserting the contents of the one or more header fields into themessage body 354, the one or more header fields can then beautomatically protected when the message 350 is encoded at 660 a usingexisting standards and protocols for facilitating secure messagecommunication, which typically encode the message body 354 of a message350 but not the message header 352. This may allow existing standardsand protocols for encoding to be used and the recipient's device doesnot have to be specially configured to be able to decode the message 350(e.g. a custom application specifically designed to process these typesof messages 350 would not be required).

At 640 a, subsequent to the insertion of contents of the one or moreheader fields to be protected into the message body 354 at 630 a, themessage header 352 can be optionally modified. In one embodiment, theoriginal contents of the one or more header fields to be protected maybe deleted, and the header fields left blank. Effectively, thecombination of inserting the contents of the one or more header fieldsto be protected into the message body 354 at 630 a and deleting theoriginal contents of the one or more header fields to be protected at640 results in the contents of the one or more header fields to beprotected being moved into the message body 354.

In another embodiment, the original contents of the one or more headerfields to be protected may be modified to indicate that one or more ofthe header fields have been protected. By way of illustration, each ofthe header fields that have been protected may be modified to say, forexample: “HEADER FIELD ENCRYPTED”, “HEADER FIELD ELIDED”, or “HEADERFIELD IN BODY”. By modifying the message header 352 as described above,this provides confidentiality of the contents of the header fields,while explicitly notifying recipients that the original contents can beretrieved.

In another embodiment, the contents of one or more header fields to beprotected may not be deleted or modified at 640 a, but is insteadretained in the message header 352 “as is” (i.e. unchanged from theoriginal). This would allow for a message recipient to manually check(i.e. by visual comparison) if any of the header fields in the messageheader 352 have been tampered with, by comparing the contents of theheader fields in the message header 352 as received with those asinserted into the message body 354 (after the message body is decoded,where necessary). Alternatively, this check may be performedautomatically at the message recipient's device in a variant embodiment,as will be described in further detail below in accordance with methods700 c and 700 d of FIGS. 7C and 7D.

At 650 a, a disclaimer can be optionally inserted into the message body354 to indicate that one or more header fields have been protected. Thedisclaimer may comprise text such as, for example: “One or more headerfields in this electronic mail message have been protected by insertingthe protected header fields into the message body.” By inserting adisclaimer, this allows message recipients at computing devices usingmessaging applications that do not support the automatic processing ofmessages that have been modified to protect the header field contents asdescribed herein, to understand why the contents of one or more headerfields have been inserted into the message body 354.

At 660 a, the message 350 (specifically, at least the message body 354and possibly message attachments 356), with the contents of the one ormore header fields to be protected inserted therein at 630 a, issecurely encoded by one of a number of known standards and protocols forfacilitating secure message communication.

At 670 a, the message is then transmitted to the intended messagerecipient(s).

FIG. 6B is a flowchart illustrating method 600 b, a specific variationof method 600 a of FIG. 6A. The flowchart in FIG. 6B is similar to theflowchart in FIG. 6A except that the one or more header fields to beprotected specifically comprise a subject field. Each act, 610 b to 670b, is analogous to a corresponding act 610 a to 670 a of FIG. 6Arespectively, and the reader is directed to the description of FIG. 6Afor further details.

Referring next to FIG. 7A, a flowchart illustrating acts of a method 700a of receiving an encoded message (e.g. message 350 of FIG. 5) at acomputing device (i.e. a message recipient's device) from a messagesender at another computing device, wherein the contents of one or moreprotected header fields have been inserted into the message body (e.g.message body 354 of FIG. 5), is shown, in accordance with at least oneembodiment.

By way of illustration, references are made below to the parts of theexample message as shown in FIG. 5.

In at least one embodiment, at least some of the acts of the method areperformed by a processor executing an application residing on acomputing device, such as a mobile device (e.g. mobile device 100 ofFIG. 1). In variant embodiments, the application may reside on acomputing device other than a mobile device. In at least one embodiment,the application is an e-mail application, although the acts of themethod may be performed in the execution of one or more differentapplications in variant embodiments.

At the recipient's computing device, an encoded message 350 (e.g. anencoded e-mail message) received from a message sender at 710 a isprocessed by first decoding the encoded message 350 at 720 a using oneof a number of known standards and protocols for facilitating securemessage communication.

At 725 a, the message body 354 of the decoded message 350 may optionallybe checked for whether a disclaimer has been inserted therein (e.g. inaccordance with act 650 a of FIG. 6A as previously described) toindicate that one or more header fields have been protected. Aspreviously described, the presence of a disclaimer allows messagerecipients at computing devices using messaging applications that do notsupport the automatic processing of messages that have been modified toprotect header field contents, as described herein, to understand whythe contents of one or more header fields have been inserted into themessage body 354. At 725 a, when a disclaimer is located in the messagebody 354, the disclaimer may be automatically removed from or hidden inthe message body 354.

In one embodiment, the decoded message 350 can be automaticallyprocessed in accordance with subsequent acts of method 700 a so that thecontents of one or more protected header fields can be extracted (e.g.viewed and/or verified) from the message body 354. In one exampleembodiment, the extracting comprises: searching the message body 354 ofthe decoded message 350 for the contents of the one or more protectedheader fields inserted therein, at 730 a; and inserting the contents ofthe one or more protected header fields as located in the message body354, back in the message header 352 of the decoded message 350, at 750a. In some of these embodiments, the extracting may always occur.However, in other embodiments, the extracting may only occur if one ormore header fields in the decoded message 350 had been modified (e.g. inaccordance with 640 a of FIG. 6A as previously described) to indicatethat one or more of the header fields has been protected, with therespective header field stating for example: “HEADER FIELD ENCRYPTED”,“HEADER FIELD ELIDED”, or “HEADER FIELD IN BODY”.

However, for non-conforming legacy applications (i.e. applications thatdo not specifically support the processing of encoded messages whereinthe header fields in the message header are protected in accordance withembodiments described herein), acts 730 a and 750 a may not be performedby the application, but may instead be performed manually by the messagerecipient.

Further details in respect of acts 730 a and 750 a are now provided. At730 a, a determination may be optionally made as to whether the messagebody 354 of the decoded message 350 contains the contents of one or moreprotected header fields, inserted in accordance with act 630 a (FIG. 6A)as previously described, for example. Message body 354 of the decodedmessage 350 may be searched for one or more protected header fieldsinserted therein. For example, as previously described, the contents ofthe one or more protected header fields may have been inserted into themessage body 354 as one or more additional lines of text, for example,as one or more additional lines of text prefaced by a description:“Secure <name of header field>: <contents of header field>” (e.g.“Secure subject: Do you want to go for lunch?”). Accordingly, themessage body 354 may be searched for the additional lines of textprefaced by a specific description, and the lines of text as containingthe contents of a protected header field may be identified.

If the contents of one or more protected header fields are not locatedin the search of the message body 354 at 730 a, then this indicates thatthe header fields 352 of the message 350 have not been protected inaccordance with method 600 a described in FIG. 6A and the entirety ofthe message 350 as it is received may be displayed at 760 a for themessage recipient.

If, however, the contents of one or more protected header fields arelocated in the search of the message body 354 at 730 a, then thisindicates that the header fields of the message 350 have been protectedin accordance with method 600 a described in FIG. 6A. At 750 a, theheader fields in the message header 352 may be reset by insertingcontents of the one or more header fields as located in the message body354 of the decoded message 350 at act 730 a back into the message header352 for display to the user. The resetting of the header fields in themessage header 352 with the contents of header fields located in themessage body 354 of the decoded message 350 ensures the integrity of themessage header 352, as it is typically only the message body 354 (andnot the message header 352) which is encoded using existing standardsand protocols for facilitating secure message communication. Theresetting of the header fields at this stage (e.g. before the receivedmessage is made available to a user for display) may also allow forfaster display and searching of the message 350 in a message list by auser for example, when the received message is subsequently retrieved.

Additionally, act 750 a may further comprise deleting the contents ofone or more header fields as located in the message body 354 of thereceived decoded message 350 on resetting the message header 352.

In some embodiments, the resetting of one or more header fields at 750 aneed not be performed immediately subsequent to 730 a, but may insteadbe deferred until the opening of the message 350 is initiated by themessage recipient. Resetting the header fields earlier may allow themessage to be displayed more quickly when the user ultimately decides toview the message. On the other hand, processing power may be conservedby deferring the act of resetting the header fields, in the event that aparticular message is never opened.

Subsequent to resetting the message header 352 with the one or moreheader fields to be protected located in the message body 354 of thedecoded message 350 at 750 a, the message 350 may be displayed at 760 ain a message listing.

In one example implementation, in addition to displaying the messageheader 352 and message body 354, the display may comprise a bar, icon,highlighting, or other indicia, or a combination thereof, in a userinterface that indicates to the message recipient that both the messageheader 352 and message body 354 have been protected, as illustrated inthe examples provided in FIGS. 9A and 9B which will be described in moredetail below. The indicia may indicate which of the one or more headerfields have been protected. For example, the indicia may be a bar,wherein at least a part of the bar is displayed adjacent to the one ormore protected header fields in the message header. As a furtherexample, the indicia may be an icon. The icon may be displayed adjacentto the one or more protected header fields in the message header, forexample. As another example, the indicia may be that the one or moreprotected header fields in the message header are highlighted and/orthat data in the one or more protected header fields in the messageheader are highlighted. As another example, the indicia may comprise acombination of features.

FIG. 7B is a flowchart illustrating method 700 b, a specific variationof method 700 a of FIG. 7A. The flowchart in FIG. 7B is similar to theflowchart in FIG. 7A except that the one or more protected header fieldsspecifically comprise a subject field. Each act, 710 b to 760 b, isanalogous to a corresponding act 710 a to 760 a of FIG. 7A respectively,and the reader is directed to the description of FIG. 7A for furtherdetails.

Reference is now made to FIG. 7C, where a flowchart illustrating acts ofa method 700 c of receiving an encoded message at a computing device(i.e. a message recipient's device) from a message sender at anothercomputing device, wherein the contents of one or more protected headerfields have been inserted into the message body 354, is shown inaccordance with at least one embodiment. Each act 710 c to 780 c isanalogous to a corresponding act 710 a to 780 a of FIG. 7A respectively,and the reader is directed to the description of FIG. 7A for furtherdetails. However, method 700 c of FIG. 7C further differs from method700 a of FIG. 7A in that the flow of method acts does not proceeddirectly from searching the message body 354 of the decoded message 350for the contents of one or more protected header fields inserted therein(i.e. act 730 c) to resetting the message header 352 with the one ormore protected header fields located in the message body 354 of thedecoded message 350 (i.e. act 750 c). Instead, method 700 c assumes thatthe original contents of the header fields to be protected were left inthe respective header fields. Method 700 c additionally comprisesperforming a comparison of the contents of the one or more protectedheader fields located in the message body 354 of the decoded message 350with the corresponding header fields of the message header 352.

Accordingly, if it is determined, at 770 c, that the contents of the oneor more protected header fields as located in the message body 354 donot match the corresponding header fields of the message header 352,then this indicates that the header fields of the message 350 have beentampered with, and an indicia may optionally be provided to the messagerecipient to indicate so at 780 c. For example, a warning or an errormessage can be shown to the message recipient when the message 350 isopened for display at 760 c. The warning or error message may read, forexample: “ALERT! One or more header fields in this electronic mailmessage have been tampered with during communication.” As a furtherexample, an icon indicating that there is a mismatch may be displayed.As a further example, the indicia may be that the header fields of themessage 350 are not displayed in the message list at 760 c.

Notwithstanding that the contents of the one or more protected headerfields as located in the message body 354 do not match the correspondingheader fields of the message header 352, method 700 c may optionallyproceed to 750 c where the header fields in the message header 352 maybe reset with the one or more header fields located in the message body354 of the decoded message 350, as previously described with referenceto 750 a of FIG. 7A. Alternatively, the flow of method acts may proceeddirectly to 760 c from 780 c (not explicitly shown in FIG. 7C).

On the other hand, if it is determined that the contents of the one ormore protected header fields as located in the message body 354 matchthe corresponding header fields of the message header 352 at 770 c, theflow of method acts may proceed to 760 c.

At 760 c, the message 350 may be displayed in a message listing, aspreviously described with reference to 760 a of FIG. 7A.

FIG. 7D is a flowchart illustrating method 700 d, a specific variationof method 700 c of FIG. 7C. The flowchart in FIG. 7D is similar to theflowchart in FIG. 7C except that the one or more protected header fieldsspecifically comprise a subject field. Each act 710 d to 780 d isanalogous to a corresponding act 710 c to 780 c of FIG. 7C respectively,and the reader is directed to the description of FIGS. 7A to 7C forfurther details.

To facilitate a better understanding of a number of features of theembodiments described herein, example messages 350 are provided in FIGS.8A to 9B, by way of illustration only. It will be understood that thegeneral format and content of messages 350 displayed in a user interfacemay differ in variant implementations.

Referring first to FIGS. 8A and 8B, examples of messages 350 from theperspective of a message sender are shown generally as 800 a and 800 b.FIG. 8A shows an example of a message 350 with no message data in themessage body 354. Where there is no message data in the message body354, the subject field of the message 350 typically contains the entirecontent of the message 350. Similarly, FIG. 8B shows an example of amessage 350 with no message data in the message body 354 other than asignature (or tagline) 840 b, identifying the message sender, forexample. A recipient of a message 350 that comprises only a signature(or tagline) 840 b in the message body 354 might assume, possibly inerror, that the message originates from the person identified in thesignature and that the message has not been tampered with.

In these examples, a processor executing an application residing on amobile device 100 processes the message 350 displayed in a display 110of mobile device 100 after the user of the mobile device 100 hascomposed it. The message 350 may comprise some message headerinformation 352 and, optionally, message data (not shown in FIG. 8A) inthe message body 354. In these examples, the message header 352comprises a “To” field 810, a “Cc” field 820, and a “Subject” field 830a. However, the message header 352 may optionally comprise additionalheader fields such as “Bcc”, “Date”, and “Reply-To”, as previouslydescribed, or different header fields.

In accordance with the example embodiment described with reference tomethod 600 b and FIG. 6B, it may be desired that the subject field 830 aof the message 350 be protected (e.g. in the message illustrated in FIG.8A). Accordingly, as illustrated in FIGS. 8C, 8D and 8E, the contents ofthe subject field 830 a in the message header 352 may be inserted (seee.g. act 630 b of method 600 b) into the message body 354, prior toencoding (see e.g. act 660 b of method 600 b) and transmitting (see e.g.act 670 b of method 600 b) the message 350 to a message recipient.Although not shown in the examples of FIGS. 8C to 8E, persons skilled inthe art will appreciate that the subject field 830 b of the message 350may also be protected by inserting the contents of the subject field 830b in the message header 352 into a message body 354 that only comprisesa signature or tagline (see FIG. 8B) or into a message body 354 thatcontains additional and/or other message data, prior to encoding andtransmitting the message 350 to a message recipient.

FIG. 8C illustrates the content of a message where the subject field 830c in the message header 352 is not modified (e.g. act 640 b of method600 b is not performed) and a disclaimer has not been inserted into themessage body 354 (e.g. act 650 b of method 600 b is not performed). Itwill be understood by persons skilled in the art that the message 350 isshown herein for illustrative purposes only, and the message sender maynot see the message 350 in this processing state (i.e. the user may notsee the contents of the subject field to be protected 830 c beinginserted into the message body 354).

Alternatively, FIGS. 8D and 8E illustrate the contents of message 350subsequent to the modification of the subject field 830 d and 830 e (seee.g. act 640 b of method 600 b) and the insertion of a disclaimer in themessage body 354 (see e.g. act 650 b of method 600 b) in variantimplementations. In FIG. 8D, the original content of the subject field830 d is deleted. In FIG. 8E the original content of the subject field830 e is modified to say “<subject encrypted>” to indicate that thesubject field has been protected. It will be understood by personsskilled in the art that the message 350 is shown herein for illustrativepurposes only, and the message sender may not see the message 350 inthis processing state (i.e. the user may not see changes made to thesubject field, and/or the insertion of the disclaimer).

Referring next to FIGS. 9A and 9B, examples of messages 350 from theperspective of a message recipient are shown generally as 900 a and 900b. In these two examples, a processor executing an application residingon a mobile device 100, for example, processes the message 350 fordisplay in a display 110 of mobile device 100 after the user of themobile device 100 (i.e. the message recipient) has received it from themessage sender. The messages 350 each comprise a subject that has beenprotected and inserted into the message body 354. The portion ofmessages 350 include some message header information 352, and,optionally, message data (not shown in the examples of FIGS. 8A to 8E)in the message body 354. In these examples, the message header 352comprises a “From” field 910, a “Cc” field 920, and a “Subject” field930 a and 930 b. However, the message header 352 may optionally compriseadditional header fields such as “Bcc”, “Date”, and “Reply-To”, aspreviously described, or different header fields. In addition todisplaying the message header 352 and message body 354, the display 110may comprise a bar 950, for example, indicating that the message header352 and the message body 354 have been protected. The bar 950 may bedisplayed adjacent to the one or more protected header fields in themessage header to indicate which of the one or more header fields havebeen protected.

FIG. 9A illustrates message 350 being displayed after the performance ofmethod 700 b on the message recipient's device. Here, subject field 930a in message header 352 has been reset with the protected subject aslocated in the message body 354 a.

FIG. 9B illustrates message 350 being displayed after the performance ofmethod 700 d on the message recipient's device, where it was determinedat 770 d that the protected subject field located in the message body354 did not match the subject field 930 b as provided in the messageheader 352 of the message as received. Accordingly, a warning message960 is shown to the message recipient to indicate that message 350 hasbeen tampered with.

Typically the entire content of a header field will be inserted into themessage body for protection, but in a variant embodiment, only a portionof the content of a given header field may be inserted into the messagebody for protection.

The acts of the method of transmitting an encoded message 350 from acomputing device to a message recipient, and the acts of the method ofreceiving an encoded message 350 from a message sender at a computingdevice in any of the embodiments described herein may be provided assoftware instructions executable by a processor (e.g. microprocessor 102of mobile device 100) stored on computer-readable storage media.

Although electronic mail messages are usually sent comprising data inthe message body, sometimes messages may be sent comprising only data ina subject field of the message header 352 and without any data in themessage body 354 (i.e. an empty message body 354). In at least someexample embodiments described herein, the determination as to whetherthe subject field in the message header 352 is to be protected at 610 bof method 600 b of FIG. 6B may comprise a determination as to whetherthe message body 354 is empty (i.e. there is no data contained therein).This may have particular advantages since when the message body 354 of amessage 350 is empty, this is usually because the content of the entiremessage is actually contained within the subject field in the messageheader 352 of the message 350.

It will be understood by persons skilled in the art that in the case ofsigned only messages (i.e. the message is not encrypted), the content ofthe one or more protected header fields may be extracted from themessage body (e.g. to be shown in a message list or to reset the one ormore protected header fields) without the message data in the messagebody 354 having to be first decrypted.

In variant embodiments, the contents of the one or more protected headerfields extracted from the message body may be stored in a memory (e.g. anon-volatile memory) of the computing device. It may be desirable tostore the contents of the one or more protected header fields extractedfrom the message body 354 when the message body 354 is decrypted,independent of the message 350, especially where the message body 354may be subsequently re-encrypted for storage on the computing device.

Some computing devices may offer content protection capabilities.Generally, content protection provides for the automatic encryption ofdata that is stored on the computing device upon locking of the device,so that an attacker cannot access the data. This functionality may beparticularly useful for securing potentially sensitive or personal data,including e-mail messages and addresses, calendar data, accessed webcontent and browser histories, and note or task data, for example. Ifcontent protection is enabled, then such data, when stored on thecomputing device, may be encrypted with a content protection key whenthe computing device is locked. In a variant embodiment, on a contentprotected computing device, the contents of one or more protected headerfields may be extracted from the message body and stored along with themessage (while not encrypted with the encryption key which typicallyprotects that message body) so that the contents of the one or moreprotected header fields are always available when the computing deviceis unlocked (the content protection key provides security for the datawhen the computing device is locked), even if the body of the message issubsequently re-encrypted for storage on the computing device inencrypted form.

As used herein, the wording “and/or” is intended to represent aninclusive-or. That is, “X and/or Y” is intended to mean X or Y or both.Moreover, “X, Y, and/or Z” is intended to mean X or Y or Z or anycombination thereof.

A number of embodiments have been described herein. However, it will beunderstood by persons skilled in the art that other variants andmodifications may be made without departing from the scope of theclaimed embodiments appended hereto.

1. A method of transmitting an encoded message from a computing deviceto a message recipient device, the message comprising a message headerand a message body, the message header comprising a plurality of headerfields, the method comprising: the computing device inserting content ofone or more header fields to be protected of the plurality of headerfields into the message body prior to transmission of the message to themessage recipient device; replacing the content of the one or moreheader fields to be protected with one or more respective notices,wherein the one or more respective notices indicate that the content ofthe one or more header fields to be protected is protected; encoding themessage body; and after said encoding, transmitting the message to themessage recipient device, such that when the message is received andprocessed by the message recipient device, the content of the one ormore header fields to be protected, that was inserted into the messagebody by the computing device, is extracted from the message body andinserted back into the one or more header fields of the message header,and when the message is displayed in a user interface of the messagerecipient device, the user interface is displayed with indiciaindicating that the one or more header fields to be protected in themessage header have been protected.
 2. The method of claim 1, furthercomprising: determining, prior to inserting the content into the messagebody, which of the plurality of header fields are to be protected. 3.The method of claim 2, wherein the determining is performed based on aconfiguration setting.
 4. The method of claim 3, wherein, theconfiguration setting is provided in an information technology (IT)policy.
 5. The method of claim 2, wherein the determining comprisesreceiving input, via a user interface of the computing device, thatidentifies the one or more header fields to be protected of theplurality of header fields.
 6. The method of claim 5, wherein themessage is composed at the computing device, and the input is receivedprior to composition of the message.
 7. The method of claim 5, whereinthe input is received upon installation of an application at thecomputing device that is configured for transmitting the message.
 8. Themethod of claim 5, wherein the input is received upon a powering on ofthe computing device.
 9. The method of claim 1, wherein the computingdevice comprises a mobile device.
 10. The method of claim 1, wherein theone or more header fields to be protected comprises a subject field. 11.A computer-readable medium storing instructions, which when executed bya processor, cause the processor to perform a method of transmitting anencoded message from a computing device to a message recipient device,the message comprising a message header and a message body, the messageheader comprising a plurality of header fields, the method comprising:the computing device inserting content of one or more header fields tobe protected of the plurality of header fields into the message bodyprior to transmission of the message to the message recipient device;replacing the content of the one or more header fields to be protectedwith one or more respective notices, wherein the one or more respectivenotices indicate that the content of the one or more header fields to beprotected is protected; encoding the message body; and after saidencoding, transmitting the message to the message recipient device, suchthat when the message is received and processed by the message recipientdevice, the content of the one or more header fields to be protected,that was inserted into the message body by the computing device, isextracted from the message body and inserted back into the one or moreheader fields of the message header, and when the message is displayedin a user interface of the message recipient device, the user interfaceis displayed with indicia indicating that the one or more header fieldsto be protected in the message header have been protected.
 12. Acomputing device comprising a processor and a memory storinginstructions for transmitting an encoded message from the computingdevice to a message recipient device, the message comprising a messageheader and a message body, the message header comprising a plurality ofheader fields, wherein when the instructions are executed by theprocessor, the processor is configured to: insert content of one or moreheader fields to be protected of the plurality of header fields into themessage body prior to transmission of the message to the messagerecipient device; replace the content of the one or more header fieldsto be protected with one or more respective notices, wherein the one ormore respective notices indicate that the content of the one or moreheader fields to be protected is protected; encode the message body; andafter said encoding, transmit the message to the message recipientdevice, such that when the message is received and processed by themessage recipient device, the content of the one or more header fieldsto be protected, that was inserted into the message body by thecomputing device, is extracted from the message body and inserted backinto the one or more header fields of the message header, and when themessage is displayed in a user interface of the message recipientdevice, the user interface is displayed with indicia indicating that theone or more header fields to be protected in the message header havebeen protected.
 13. The computing device of claim 12, wherein theprocessor is further configured to: determine, prior to inserting thecontent into the message body, which of the plurality of header fieldsare to be protected.
 14. The computing device of claim 13, wherein thedetermining is performed based on a configuration setting.
 15. Thecomputing device of claim 14, wherein, the configuration setting isprovided in an information technology (IT) policy.
 16. The computingdevice of claim 13, wherein to determine which of the plurality ofheader fields are to be protected, the processor is further configuredto receive input, via a user interface of the computing device, thatidentifies the one or more header fields to be protected of theplurality of header fields.
 17. The computing device of claim 16,wherein the message is composed at the computing device, and the inputis received prior to composition of the message.
 18. The computingdevice of claim 16, wherein the input is received upon installation ofan application at the computing device that is configured fortransmitting the message.
 19. The computing device of claim 16, whereinthe input is received upon a powering on of the computing device. 20.The computing device of claim 12, wherein the computing device comprisesa mobile device.
 21. The computing device of claim 12, wherein the oneor more header fields to be protected comprises a subject field.